WebSphere Deployment

Initial System Configuration

Database Drivers

Create a directory for the database drivers for your database. Copy the necessary driver .jar files into this directory.
Example:

AIX or Linux: /opt/oracle/db_drivers
Windows: C:\oracle\adminconsole\db_drivers

• Oracle 12.1 – The necessary driver, ojdbc8-12.2.0.1.jar, is included in the libs directory of the AdminConsole Media Pack.

• IBM DB2 – db2jcc4 jar is included with the purchase of the DB2 software. This file is not available for download. Contact your IT department if you need assistance locating these files.

• Microsoft SQL - download the sqljdbc4.jar library version 4.0 from https://mvnrepository.com/artifact/com.microsoft.sqlserver/sqljdbc4/4.0

Note: Each version of DB2 requires specific drivers. The files above correspond with DB2 10.5.

AdminConsole Setup

Note: For a WebSphere 9.0.0.9 deployment, the .jar files need to be installed only once. If AdminConsole Is reinstalled, the existing files may be re-used.

1. Create a directory on the WebSphere server to store various configuration files for AdminConsole(e.g., /opt/oracle/adminconsole/ or C:\oracle\adminconsole).
2. Create sub-directories inside the directory from Step 4 called conf and libs.

Note: Make a note of the path to the libs directory. It will be used later in the classpath for setting up the AdminConsole Shared Library.

3. Copy the following files from the installation media to the libs sub-directory:

   • commons-logging-1.2-1e55e8f.jar

   • el-api-2.2.jar

   • eclipselink-2.7.10.jar

   • log4j-api-2.18.0.jar

   • jakarta.persistence-2.2.3.jar

4. Open aspectj-1.9.1.jar with an unzipping software and copy aspectjrt.jar and aspectjweaver.jar from the lib folder into the libs sub-directory.

5. Download aspectj-1.9.1.jar from https://www.eclipse.org/downloads/download.php?file=/tools/aspectj/aspectj-1.9.1.jar

6. Use a text editor to open the ac.properties file that was copied to the server. The ac.properties file contains properties for Oracle and DB2 database types, with the Oracle settings active by default. The inactive settings are commented out with a '#' character at the start of each line. To change a setting, remove the '#' from the required property setting, and insert it at the beginning of the setting you want to de-activate.

7. The properties setting must match the type of database being used. The two properties that are used to do this are:
• application.databaseType
• jpa.databasePlatform

Note: Refer to the latest System Properties document in the Oracle Insurance Policy Administration Documentation Library published on the OHC for a complete list of all properties and allowed values.

8. Identify the default locale in the ac.properties file. The locale selected will determine the translation that is loaded in the database for AdminConsole when it launches. The default setting is English.

   • application.defaultLocale

9. If the database is Oracle, skip this step. If using a DB2 database, modify the ac.properties file to include configuration for case-insensitive searching:

   • Modify the ac.properties file to change the following line from the default setting of "false" to "true": search.field.text.caseInsensitive=true.

10. Use a text editor to open the logging.properties file that was copied to the server.

    • Edit the path mention for property "java.util.logging.FileHandler.pattern" with new application log location i.e. if application log location is /home/adminconsole/logs then set this value as java.util.logging.FileHandler.pattern = %h/adminconsole/logs/adminconsole%u.log. Also same time make sure that directory is created and has r/w permission.

Create and Configure Admin Console

Using a web browser, connect to the Administrative Console using the appropriate server name and 9080 as the default port

(Ex: server_name:9080/adminCenter" class="external-link" rel="nofollow"). http://server_name:9080/adminCenter.

Note: These instructions assume that a fresh installation of the application server was performed. All configuration settings must use the default settings unless otherwise noted. In case the application server has been used for previous deployments, create a new application server specifically for the deployment of the Admin Console environment.

Create the Admin Console Application Server

1. Navigate to /path/to/ibm-liberty/IBM/WebSphere/Liberty/bin

2. Execute ./server create AdminConsole

3. A directory 'AdminConsole' will be created under /path/to/ibm-liberty/IBM/WebSphere/Liberty/usr/servers with the file 'server.xml' containing all the configurations.

4. Edit 'server.xml' file to configure ListenAddress, ListenPorts, Application Library Path, Configuration File Path, Data Sources, etc...

5. Refer to the below 'server.xml' file for the sample configurations for the AdminConsole.

<?xml version="1.0" encoding="UTF-8"?>
<server description="new server">
   <!-- Enable features -->
   <featureManager>
        <feature>jsp-2.3</feature>
	<feature>adminCenter-1.0</feature>
	<feature>websocket-1.1</feature>
	<feature>jdbc-4.1</feature>
	<feature>jaxrs-2.0</feature>
	<feature>jaxws-2.2</feature>
	<feature>appSecurity-2.0</feature>
	<feature>restConnector-2.0</feature>
	<feature>jndi-1.0</feature>
        <feature>distributedMap-1.0</feature>
	<feature>el-3.0</feature>
	<feature>jaxb-2.2</feature>
	<feature>jaxrsClient-2.0</feature>
	<feature>json-1.0</feature>
	<feature>servlet-3.1</feature>
   </featureManager>
   <variable name="defaultHostName" value="fsgbu-mum-146.snbomprshared1.gbucdsint02bom.oraclevcn.com" />
<basicRegistry id="basic">
      <user name="admin" password="Welcome1" />
      <user name="nonadmin" password="Welcome1" />
      <user name="qatester3" password="qatester3" />
      <user name="acadmin" password="acadmin123" />
      <user name="acpurge" password="acpurge123" />
      <group name="ACADMIN_GRP">
	<member name="qatester3"/>
	<member name="acadmin"/>
      </group>
     <group name="ACPurgeLog_GRP">
	<member name="acpurge"/>
      </group>
   </basicRegistry>
   <administrator-role>
      <user>admin</user>
   </administrator-role>
   <remoteFileAccess>
      <writeDir>${server.config.dir}</writeDir>
   </remoteFileAccess>

   <!-- To access this server from a remote client add a host attribute to the following element, e.g. host="*" -->
   <httpEndpoint id="defaultHttpEndpoint" host="*" httpPort="9087" httpsPort="9050" />

   <!-- Automatically expand WAR files and EAR files -->
   <applicationManager autoExpand="true"/>
	
   <!-- Admin Console application section -->
   <webApplication contextRoot="AdminConsole" location="AdminConsole.war">
	<classloader delegation="parentLast" >
		<commonLibrary>
			<fileset includes="*" dir="/scratch/oipa/IBM/OIPA/ADMINCONSOLE/lib/"/>
			<fileset includes="*" dir="/scratch/oipa/IBM/OIPA/ADMINCONSOLE/conf/"/>
			<folder dir="/scratch/oipa/IBM/OIPA/ADMINCONSOLE/conf"/>
			<file name="/scratch/oipa/IBM/OIPA/ADMINCONSOLE/conf/ac.properties"/>
		</commonLibrary>
	</classloader>
	<application-bnd>
        	<security-role name="AC_ADMIN">
          		<group name="ACADMIN_GRP"/>
        	</security-role>
		<security-role name="AC_PURGE_LOG">
          		<group name="ACPurgeLog_GRP"/>
        	</security-role>
	        <security-role name="AllAuthenticated">
            		<special-subject type="ALL_AUTHENTICATED_USERS" />
	        </security-role>
    	</application-bnd>
    </webApplication>
	
    <dataSource id="ADMINCONSOLEDS" jndiName="ADMINCONSOLEDS" transactional="false" type="javax.sql.XADataSource">
		<jdbcDriver libraryRef="OracleLib"/>
        <properties.oracle driverType="thin" serverName="fsgbu-mum-502.snbomprshared1.gbucdsint02bom.oraclevcn.com" portNumber="1521" databaseName="orcl" password="aconsole" user="aconsole" />
    </dataSource>

   <library id="OracleLib">
      <file name="/scratch/oipa/IBM/OIPA/ADMINCONSOLE/lib/ojdbc11-21.3.0.0.jar"/>
   </library>
	
   <logging hideMessage="SRVE9967W" />
</server>

Note: Use the above 'server.xml' file for reference purpose only.